row lock造句
- The database engine determines when row locks are used
數(shù)據(jù)庫引擎確定何時使用行鎖。 - Describes how the jdbc driver supports row locking
說明jdbc驅(qū)動程序如何支持行鎖定。 - Row locks are allowed when accessing the index
在訪問索引時允許行鎖。 - Row integrity is ensured with row locking
通過行鎖定確保行的完整性。 - Cumulative number of row locks requested
請求的行鎖的累積數(shù)量。 - The statement acquires 3 , 000 row locks in the clustered index for
的聚集索引中獲取3 , 000個行鎖，在 - Cumulative number of times the database engine waited on a row lock
數(shù)據(jù)庫引擎等待行鎖的累積次數(shù)。 - Specifies whether row locks are allowed
指定是否允許行鎖。 - Total number of milliseconds the database engine waited on a row lock
數(shù)據(jù)庫引擎等待行鎖的總毫秒數(shù)。 - And at least 5 , 000 row locks in the clustered index for
的聚集索引中獲取至少5 , 000個行鎖，但是仍無法訪問 - It's difficult to see row lock in a sentence. 用row lock造句挺難的
- 0 index does not allow row locks
0 =索引不允許行鎖。 - Specifies that row locks are taken when page or table locks are ordinarily taken
指定通常采用頁鎖或表鎖時，采用行鎖。 - Understanding row locking
>了解行鎖定 - Row locks are not used
未使用行鎖。 - Read operations acquire no page or row locks ; only sch - s table locks are acquired
讀取操作不獲取頁鎖或行鎖，只獲取sch - s表鎖。 - Read operations require only sch - s table level locks and no page or row locks
讀取操作只需要sch - s表級別的鎖，不需要頁鎖或行鎖。 - For easier reading , the following db2pd output has been modified to remove all but the row locks
為了閱讀方便，對下面的db2pd輸出進行了修改，刪除除了鎖定的行以外的所有行。 - Intent locks , row locks , and page locks all count toward the escalation count , unless they are temporary table locks
除非屬于臨時表鎖，否則意向鎖、行鎖和頁鎖都將計入升級統(tǒng)計中。 - Using the paglock or tablock table hints to have the database engine use page , heap , or index locks instead of row locks
使用paglock或tablock表提示，使數(shù)據(jù)庫引擎使用頁、堆或索引鎖而不是行鎖。 - When the total of intent locks , row locks and page locks on a specific table exceeds the escalation threshold , escalation occurs
當特定表上意向鎖、行鎖和頁鎖的總數(shù)超出升級閾值時，就會進行升級。
手機版